Track binary size over time #7005
Conversation
|
@kkaefer, thanks for your PR! By analyzing the history of the files in this pull request, we identified @yhahn, @mikemorris and @tobrun to be potential reviewers. |
kkaefer
force-pushed
the
binary-size-metrics
branch
from
ef6720b to
8bd59bb
Compare
|
Can we get this approved so that we can start collecting sizes? |
|
@kkaefer Can you record somewhere how to view the CloudWatch history? |
|
Follow up in #7092 |
|
You can view the binary size log at https://mapbox.github.io/mapbox-gl-native/metrics/binary-size/ |
|
@kkaefer this is really nice, could the same idea be used for tracking metrics like memory consumption? |
|
@tmpsantos yeah; have a look at |
Add logging to CloudWatch that records binary size for Linux, Android, iOS and macOS. In the case of fat binaries, the binary size is split up to individual architectures (iOS/Android) in addition to the default archive.
The idea is that we'll have nightly builds (running in EU early morning) that create a stripped release build to approximate the size of the library in a deployed setting, and record those. Using the data stored in CloudWatch, we'll be able to generate graphs of how the binary size changes over time.